SAS Real-Time Decision Manager 5.4 is unable to write any messages that are longer than 32KB to its user log. As a result, user logs are often empty or incomplete. Follow the steps below to get the full user log information (and more) in the macore log for a given campaign execution.

Set a higher logging level

Keep in mind that the change that is described below requires you to restart SAS^® Remote Services and the SAS^® Web applications on which it depends. Make these changes at a time that you can restart the application.

First, set the SDS Polling Server logging.

1. Find the directory under /Lev1 that contains the SDS Polling Server's sdslogconfig file. This file is usually in ...Lev1\Applications\SASRealTimeServerConfig5.4. There is another file in the directory named sdslogconfig.trace.xml. Edit the SDS Polling Server properties under the Server Manager plug-in for SAS^® Management Console. Copy the current command line and save it to a location from which it is easy to restore later. Substitute the fully qualified path and filename for sdslogconfig.trace.xml for the current filename, sdslogconfig.xml, after the –logcfgloc argument in the command line.
2. Close all campaigns and diagrams that use the RTDM Object Spawner.
3. Stop the RTDM Object Spawner in order to get the SDS servers to pick up the new logcfgloc argument.
4. Check that the SAS processes that are associated with the RTDM Object Spawner have stopped. Not all SAS processes are owned by the RTDM Object Spawner. If you are not sure that the correct ones have stopped and you have the option of restarting everything that creates a SAS process, then restart your SAS environment. If you restart Remote Services, remember to restart the SAS^® Marketing Automation and SAS Real-Time Decision Manager web applications after Remote Services restarts.
5. Restart the RTDM Object Spawner.

Next, set the SAS Marketing Automation logging level.

1. In SAS Management Console Foundation Services Manager, select Remote Services ► Core ► Logging Service.
2. Right-click Logging Service and select Properties.
3. On the Service Configuration tab, go to Configuration...,Contexts. Select com.sas.analytics.crm.
4. Click Edit and choose priority = DEBUG, output selected = MA. This context and priority gets the XML payload from SAS^® Decision Services.
5. Back on Contexts, select com.sas.analytics.crm.persistence ► Edit, and choose priority = INFO, output selected = MA. This selection prevents extra persistence messages from cluttering the macore log.
6. Again on Contexts, select com.sas.analytics.crm.web ► Edit and choose priority= INFO, output selected = CWS. This context is not necessary for gathering the information that you want, so you are sending it to a different location.
7. In the SAS Management Console Foundation Services Manager, select Remote Services ► Core ► Logging Service, Properties, Service Configuration, Configuration...
8. Select Outputs = MA, File Output = your-env/your-ma-core-filename.log.

Finally, set the SAS Real-Time Decision Manager logging level.

1. Back up the SASRealTimeDesignServer5.4.ear file at ...\IBM\WebSphere\AppServer\profiles\your-profile\installedApps\SASDmgr01Cell\SASReal-TimeDesignServer5.4.ear.
2. Extract the log4j.properties file from the path ...\IBM\WebSphere\AppServer\profiles\your-profile\installedApps\SASDmgr01Cell\SASReal-TimeDesignServer5.4.ear\sas.rtdm.designserver.war\WEB-INF\.
3. Edit the log4j.properties file. It should have the following contexts and values. The contexts that you need to change for your purposes are the entries that contain ph. That is, change the second and third entries, below. Note that you do not have to set full DEBUG logging. The information that you get from INFO is sufficient.

4. Package the log4j file in a ZIP file and save it to the WEB-INF directory of the RTDM Design Server WAR file, sas.rtdm.designserver.war.
5. Package the modified RTDM Design Server WAR file, sas.rtdm.designserver.war, in a ZIP file to the RTDM Design Server EAR file, SASReal-TimeDesignServer5.4.ear.
6. Redeploy the RTDM Design Server EAR file to a WebSphere Application Server and then restart the middle-tier environment for your application.

Note that setting the logging level in the following file does not have the desired effect:
\\machine\SAS\Config\Lev1\Web\Common\LogConfig\SASRealTimeDecisionManagerDesignServer-log4j.xml

Run the campaign in the correct environment

Run the decision campaign in the SAS Customer Intelligence Studio Test environment. The test environment exercises the same code within the RTDM Design Server that is exercised in the RTDM Engine Server when the campaign is run in production. The log messages that come from the RTDM Design Server are written to macore with the log settings that are listed below. These log messages include all of the information that you would get from the user log as well as some other details.

Find the information that you need by examining the SASMarketingAutomationCore5.4 (macore) log

In order to find the pertinent entries in the macore log, search for the word FlowDefinition. Find the flow definition that contains the flow ID for your campaign.

The flow ID is in the properties of the run-time flow in the RTDM Design Server repository in the SAS Management Console. When you run your campaign, the application generates a temporary run-time flow. Find this run-time flow in the RTDM Design Repository in the SAS Management Console. The description field contains the name of your campaign. The name field contains the flow ID with a "_" prefix to indicate that the flow is a temporary run-time flow.

In order to find the test case payload, search for the keywords TestInput and TestOutput.

The Design Server information that is written to macore also includes timestamps. These timestamps have the information that is needed for performance testing.

Operating System and Release Information